Fix/fix relationship set and view #1877
Conversation
|
The preview deployment is ready. 🟢 Open Preview | Open Build Logs Last updated at: 2025-05-23 09:13:51 CET |
|
The preview deployment is ready. 🟢 Open Preview | Open Build Logs Last updated at: 2025-05-23 09:13:54 CET |
...roject]/databases/database-[database]/collection-[collection]/attributes/relationship.svelte
Outdated
Show resolved
Hide resolved
| return sdk | ||
| .forProject(page.params.region, page.params.project) | ||
| .databases.listCollections(databaseId, queries, search); | ||
| .databases.listCollections(databaseId, queries); |
There was a problem hiding this comment.
So search is being removed because the component is a basic dropdown rather than a combo box where you can type to search? This will make it difficult for people to find the option they need.
There was a problem hiding this comment.
This is getting the collections from the API. The combobox is filtering on the client based on what the API returned. ATM search is defaulting as null which results in 0 results coming from the API. So ATM it's entirely broken, and this fixes that.
Updating this to the ComboBox is still something we need to do, but there is a bug that the dropdown of the combobox falls behind the modal, so you cannot use it.
TLDR: this change is going from 100% broken to usable. We need to do more work to make it good.
There was a problem hiding this comment.
@stnguyen90 its now using the combobox! @ArmanNik fixed the issue with the dropdown being behind the modal!
There was a problem hiding this comment.
So shouldn't the search be added back while making sure the search param isn't passed in the API call if the user hasn't entered any value?
| return sdk | ||
| .forProject(page.params.region, page.params.project) | ||
| .databases.listCollections(databaseId, queries, search); | ||
| .databases.listCollections(databaseId, queries); |
There was a problem hiding this comment.
So shouldn't the search be added back while making sure the search param isn't passed in the API call if the user hasn't entered any value?
What does this PR do?
Fix the pre select of the option in the relation overview of the document
Have you read the Contributing Guidelines on issues?
✅